5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
- Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-7: Predefined Fields

OPERATIONAL PHASE


This field is stored in system administration for each database and application combination. Its value can be changed from initial setup or recovery processing by means of the predefined process BEGIN LIVE OPERATIONS.

There are certain differences between the operating phases. In initial setup and recovery processing, for example, records can be deleted from files even if there is delete protection, and keys can be changed even if there is key protection. In live operations or recovery processing, modification logs are produced for any input process with a non-blank Mod Log File Name. In initial setup, mod logs are never produced. And for any input item defined with Modifiable? equal to blank, it means that the item is modifiable in initial setup and recovery processing, but not in live operations. (As an example, this allows the designer to use the same input process for initial setup and live operations, without compromising data integrity.) In addition, images and even entire frames can be skipped if the application is in live operations, by setting the parameter Skip if Live Operations? to Y for that image or frame.

  
        IF       --- OPERATIONAL PHASE          EQ     INITIAL SET UP 
 

Default Value: Taken from system administration files for a given database/application combination when a child is invoked as detached.

Valid Values: INITIAL SET UP, LIVE OPERATIONS, RECOVERY PROCESSING

Application Design Manual                                         "Powered by Appx Software"

808

©2006 By APPX Software, Inc. All Rights Reserved